docs: fleet is 23 pairs now, and why a kit-only file needs no wave - #32
Open
mcarter-astronautdev wants to merge 1 commit into
Open
docs: fleet is 23 pairs now, and why a kit-only file needs no wave#32mcarter-astronautdev wants to merge 1 commit into
mcarter-astronautdev wants to merge 1 commit into
Conversation
…wave Merging the two agent-repo installs moved the fleet 21 -> 23, which makes several present-tense counts wrong. Re-verified against a live audit run rather than incremented by hand: 23 pairs, 110 pin rows at 90f0d06, 131 files matching templates/, zero drift. - Repin-wave targets 21 -> 23. - The stub-rails-only set 3 -> 5: driver-agents@main and driver-agents-app@main join Team-Laird, The-Gathery and driver-bonsai-mcp. Full-kit targets stay 18 — the two new repos take the partial install, so neither carries claude.yml or bonsai-status-sync.yml. - The branch-protection survey is now 23 pairs; both new repos require one approving review, so the count lacking a human-approver rule stays 10. - The partial install is no longer "proposed" — it is what those two repos run. Also writes down the question this raised, since the answer is not obvious and the cost of guessing wrong is a 21-branch wave: a kit-only addition needs neither a tag nor a wave when it changes no reusable, repins no stub, and carries no uses: pin of its own. The obligation runs the other way — cutting the tag is what creates the wave, because once the latest tag is not 90f0d06 the reference check fires against all six stubs and templates/ has to be repinned and re-copied everywhere.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merging DriverDigital/driver-agents#6 and DriverDigital/driver-agents-app#2 moved the fleet 21 → 23, which makes several present-tense counts in these docs wrong. Numbers here are re-verified against a live audit run, not incremented by hand:
Changes:
driver-agents@mainanddriver-agents-app@mainjoinTeam-Laird@develop,The-Gathery@developanddriver-bonsai-mcp@main. Full-kit targets stay 18: the two new repos took the partial install, so neither carriesclaude.ymlorbonsai-status-sync.yml.studio-sulzer@mainandTeam-Laird@develop.The part worth reading
This landed a new kit file (
templates/github/lint.yml) with no tag and no wave, which is a departure from every prior kit addition, so the reasoning is now written down rather than left to be re-derived.It was correct here because
lint.ymlchanges no reusable, repins no stub, and carries nouses: DriverDigital/workflows@<sha>of its own — so nothing already deployed had to move, and the audit read clean throughout.The non-obvious part is which way the obligation runs: cutting the tag is what creates the wave. The moment the latest tag is not
90f0d066, the audit's reference check fires against all six stubs,templates/must be repinned, and the fleet must be re-copied — 23 branches — for a release whose reusables nobody touched. So a kit-only file should ride along with the next release that actually changes a reusable.v1.7.0deliberately did the opposite ("stubs repinned regardless, purely so the latest-tag comparison stays meaningful"), and that was right, because that wave was carrying kit content to the fleet. This one wasn't.